Nectar Logo

User-Centred Requirements Handbook

Telematics Engineering Logo

Phase 3. User requirements documentation


3.1 General system characteristics

Objective

Process

1. Review all the potential user requirements identified in Phases 1 and 2, particularly in Forms 1.3 User characteristics, 1.7 User goals and tasks, and 1.10 Design ideas and concepts. Copy those that relate to system characteristics into Form 3.1 below.

2. Remove any requirements that duplicate others or do not seem relevant.

3. Add any new requirements which arise from the review of this section.

Please refer to RESPECT D4.2, section 3.4 which briefly describes the establishment of an in-house usability guide. This will be a natural extension to the process of specifying general and desirable characteristics of the system.

Form 3.1 - General System Characteristics (Example)

3.1 General System Characteristics

System: New Bank machine

Pri. Ach. Ref.
Transfer from Form 1.3 User Characteristics, 2.3 Task scenarios and Form 1.10 Design Concept characteristics 1-5
*
**
***
 
Given particular consideration to older user groups who may be more reserved about new technology. 2 * 1.3.1
Use simple terminology, diagrams and pictures. 3 * 1.3.4
Design to be usable by people who may have limited reading skills. 4   1.3.5
Try to make the system conform with any accepted ad hoc standards for bank machines. 3 * 1.3.8
Use very supportive dialogues to make user feel comfortable. 2 ** 1.3.9
Develop attractive interfaces which are also easy and enjoyable to use. 1 ***
1.3.10
1.3.14
1.3.15
Ensure that results can be achieved quickly. 2 * 1.3.16
Make as attractive and simple as possible for new users. 2 * 1.3.19
Users representatives should be given the opportunity to see existing applications developed with same software. 2   1.4.4
Speech synthesis for guidance - Expensive but may be useful for those with impaired vision. 4   1.11.1
System response times should normally be <2 seconds, maximum 10 seconds. 3 *  
System should support the performance of tasks in variable order. 3 **  
Provide a good level of privacy for the user to avoid encouraging theft. 2 ***  

3.2 Organisational structure
Back to Contents

NECTAR Home Page The NECTAR Information Update The NECTAR Repository The European Journal of Engineering for Information Society Applications The NECTAR Discussion Fora